Grokking SQL for Tech Interviews
Rate this course
Ask Author
Contribute
Back to course home

1% completed

Vote For New Content
Introduction
Course Overview
What is RDBMS?
What is SQL?
A Quick Review of SQL
Read data from table
WHERE Clause
Operators
Handle NULLs in SQL
DISTINCT Clause
ORDER BY Clause
LIMIT and OFFSET
GROUP BY
HAVING
Aggregate Functions
Order of Execution
Order of SQL Query Execution
SQL Functions
Number Functions
String Functions
Date Functions
Nested Queries
Nested Query
Types of Subqueries
JOINS
Introduction
INNER JOIN
LEFT OUTER JOIN
RIGHT OUTER JOIN
FULL OUTER JOIN
SELF JOIN
SET Operations
What are SET operations?
UNION
INTERSECT
EXCEPT
A Quick Review of DDL
Keys in SQL
CREATE
ALTER
DROP
TRUNCATE
Indexes
A Quick Review of DML
INSERT
UPDATE
DELETE
Database Backup & Restore
Backup Database
Restore Database
Interview Problems - Easy
1. Major Cities
2. Not boring movies
3. Triangle Judgement
4. Biggest Single Number
5. Product Sales Analysis I
6. Product Sales Analysis II
7. Game Play Analysis I
8. Game Play Analysis II
9. Queries Quality and Percentage
10. Average Selling Price
11. Weather Type in Each Country
12. Students and Examinations
13. Ads Performance
14. Group Sold Products By The Date
15. Employee Email Verification
16. Sellers With No Sales
17. Average Time of Process
18. Find Followers Count
19. Ad-Free Sessions
20. Bikes Last Time Used
21. Daily User Engagement Levels
22. Employee Attendance Record
23. Library Book Loans
24. Customer Purchase Summary
25. Long Comments (Easy)
26. Unused Accounts
27. Patient Appointment No-Shows
28. Books and Authors
29. High School Attendance
30. Employee Absences
31. Green Product Identification (Easy)
32. Employee Department Exclusion (Easy)
33. Sales Person (Easy)
34. Employee Task Tracking (Easy)
Interview Problems - Medium
1. Winning Candidate
2. Second Degree Follower
3. 2nd Highest Salary
4. Game Play Analysis III
5. Game Play Analysis IV
6. Active Businesses
7. Product Price on a Specific Date
8. Monthly Transactions II
9. Team Scores in Football Tournament
10. Page Recommendations
11. Running Total for Different Genders
12. Evaluate Boolean Expression
13. Active Users
14. Find Interview Candidates
15. Suspicious Bank Accounts
16. Order Fulfillment Rate (Medium)
17. Last Person to Fit in the Elevator (Medium)
18. Retail Expansion Analysis (Medium)
19. Employee Collaboration Networks (Medium)
20. Second Fastest Time in Races (Medium)
1. Trips and Users
2. Human Traffic of Stadium
3. Students Report By Geography
4. Game Play Analysis V
5. Number of Transactions per Visit
6. Find the Quiet Students in All Exams
7. First and Last Call On the Same Day
8. Build the Equation
9. Longest Winning Streak
10. Dynamic Pivoting of a Table
11. Dynamic Unpivoting of a Table
12. Generate the Invoice
13. Popularity Percentage
14. Viewers Turned Streamers
15. Status of Flight Tickets
1. High Performing Employees (Easy)
2. Student Course Averages (Easy)
3. Library Book Checkout Percentage (Easy)
4. Employee Performance and Improvement Rate (Easy)
5. Find Popular Posts (Easy)
6. Main Office Assignment for Each Employee (Easy)
7. Rectangle Validation (Easy)
8. Library Book Checkouts by Date (Easy)
9. Same-Day Appointment Fulfillment (Medium)
10. Departments with High Earning Employees (Medium)
11. Students Who Attended All Courses (Medium)
12. Library Book Checkouts First Year (Medium)
13. Repeated Values in Sequence (Medium)
14. School Top Achievers by Subject (Hard)
17. Last Person to Fit in the Elevator (Medium)

Problem Statement

Table: ElevatorQueue

This table stores information about individuals waiting for an elevator. Each row includes a person's ID, their name, their weight, and their position in the queue.

+---------------+---------+
| Column Name   | Type    |
+---------------+---------+
| person_id     | int     |
| name          | varchar |
| weight        | int     |
| position      | int     |
+---------------+---------+
person_id column contains unique values.
This table contains data about all individuals queuing for an elevator.
The person_id and position columns will contain all numbers from 1 to n, where n is the number of rows in the table.
position determines the queue order for boarding the elevator, where position=1 denotes the first person in the queue and position=n denotes the last person in the queue.
weight is the weight of the individual in kilograms.

The elevator has a maximum weight capacity of 800 kilograms. It's possible that not everyone in the queue will be able to board the elevator without exceeding this limit.

Develop a solution to identify the name of the last individual who can board the elevator without surpassing the weight capacity. Assume that the first individual in the queue does not exceed the weight limit.

Return the result in the format provided in the example.

Example

Input:

ElevatorQueue table: +-----------+------------+--------+----------+ | person_id | name | weight | position | +-----------+------------+--------+----------+ | 1 | Alice | 200 | 1 | | 2 | Bob | 150 | 4 | | 3 | Charlie | 300 | 2 | | 4 | Dave | 225 | 5 | | 5 | Eve | 175 | 3 | | 6 | Fiona | 350 | 6 | +-----------+------------+--------+----------+

Output:

+------+ | name | +------+ | Eve | +------+

Try It Yourself

MYSQL

. . . .

ElevatorQueue =

Solution

To determine the last individual who can board the elevator without exceeding the 800-kilogram weight limit, we'll follow a streamlined approach that aligns directly with the SQL query provided.

  1. Order Individuals by Position: Start by arranging the individuals based on their position in the queue to respect the boarding order.
  2. Calculate Cumulative Weight: Compute a running total of weights as we move down the queue. This helps in identifying when the cumulative weight approaches or exceeds the elevator's capacity.
  3. Identify the Last Eligible Individual: From the cumulative weights, select the last person whose addition doesn't breach the 800-kilogram limit.

SQL Query

WITH CumulativeWeight AS ( SELECT name, weight, SUM(weight) OVER (ORDER BY position) AS total_weight FROM ElevatorQueue ) SELECT name FROM CumulativeWeight WHERE total_weight <= 800 ORDER BY total_weight DESC LIMIT 1;

Step-by-Step Approach

Step 1: Order by Position and Calculate Cumulative Weight

We utilize a Common Table Expression (CTE) named CumulativeWeight to:

  • Order the individuals based on their position.
  • Calculate the cumulative weight up to each person in the queue using the SUM() OVER (ORDER BY position) window function.
WITH CumulativeWeight AS ( SELECT name, weight, SUM(weight) OVER (ORDER BY position) AS total_weight FROM ElevatorQueue )

Explanation:

  • The SUM(weight) OVER (ORDER BY position) computes the running total of weights as per the queue order.
  • This CTE prepares the data for the next step by providing the cumulative weights alongside each individual's name.

Step 2: Select the Last Individual Within Capacity

From the CumulativeWeight CTE, we:

  • Filter individuals where the total_weight is less than or equal to 800 kilograms.
  • Order the filtered results in descending order of total_weight to prioritize the heaviest possible cumulative weight without exceeding the limit.
  • Limit the result to the top entry, which represents the last person who can board without surpassing the capacity.
SELECT name FROM CumulativeWeight WHERE total_weight <= 800 ORDER BY total_weight DESC LIMIT 1;

Explanation:

  • WHERE total_weight <= 800 ensures we only consider scenarios where the elevator's capacity isn't exceeded.
  • ORDER BY total_weight DESC arranges the eligible individuals so that the one with the highest cumulative weight is at the top.
  • LIMIT 1 retrieves the single name that fits the criteria, representing the last person who can board safely.

Final Output:

+------+ | name | +------+ | Eve | +------+
16. Order Fulfillment Rate (Medium)
18. Retail Expansion Analysis (Medium)
Mark as Completed

On this page

Problem Statement

Example

Try It Yourself

Solution

SQL Query

Step-by-Step Approach